-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(maintenance): drop support for Node.js 16.x #2717
Conversation
Integration tests on this branch are passing: https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/9757062917 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work on keeping the track on all the places where node16 had a special treatment!
Few notes on default node version in various places, so we can settle on either 18 or 20.
Quality Gate passedIssues Measures |
Summary
Changes
This PR drops support for Node.js 16 for Powertools for AWS Lambda (TypeScript). As discussed in the linked issue, Node.js 16 has reached EOL and its corresponding AWS Lambda managed runtime has been marked as deprecated.
Below a list of changes included in the PR:
nodejs16x
from compatible runtimes in Lambda layerObject(someObject).hasOwnProperty(someProperty)
withObject.hasOwn(someObject, someProperty)
(MDN docs)ParseError
in Parser utility to use it, as well as every envelopefetch
in e2e tests since now it's present in all supported runtimesIssue number: closes #2223
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.